…ndow

- Add runtimeType to sessionInfo so SessionControls renders Stop for transport sessions
- Expand UsageFooter render condition to include plan/quota badge metadata

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Remove subSessionsFull stripping memo, pass full SubSession[] to PanelRenderContext
- Import SubSession type directly in PanelRenderContext (prevents future type drift)
- Add compact UsageFooter to pinned SubSessionContent with model/plan/quota display
- Document compact panel contract (intentional inclusions/exclusions)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…le store data

- buildSubSessionSync: compute planLabel/quotaLabel/quotaUsageLabel fresh via
  getQwenDisplayMetadata (same as buildSessionList for main sessions)
- refreshQwenQuotaUsageLabels: re-sync sub-sessions to browser on quota update
- Revert parent-session inheritance hack — daemon provides fresh data directly

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Combine quotaLabel + quotaUsageLabel into single inline text (9px, gray)
- Plan badge (Free/Paid/BYO) stays as pill badge on the right
- Layout: "1,000/day · today 12/1000" [Free]

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- Plan/quota (e.g. "1,000/day · today 12/1000  Free") now inline small text
  in shortcuts row, left of model switcher and Solo button
- Removed from UsageFooter to avoid duplication
- Pinned panel: compact inline badge row (no SessionControls there)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…refix

On Windows with ConPTY, respawnSession was prepending
  `export IMCODES_SESSION='...'; `
to the command, then passing it through cmd.exe /c — which doesn't
understand POSIX `export` syntax, causing the respawn to fail.

Fix: extend respawnPane / conptyRespawnPane / conptyNewSession to accept
an env map.  When BACKEND === 'conpty', pass mergedEnv directly to
conptyNewSession so node-pty injects it as proper process env vars.
Keep the existing envPrefix bash-string path for tmux/wezterm.

Tests: 4 new assertions lock the conptyRespawnPane env injection contract.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…e flake on macOS

codex-watcher-refresh: after writing newerSameUuid, explicitly advance its
mtime +2s via utimes() so checkNewer() works correctly on HFS+ (1-second
mtime granularity). Without this the test is flaky on macOS CI when both
writes land within the same second.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

emitRecentHistory was added unconditionally to startWatchingSpecificFile
(codex-watcher) and activateFile (jsonl-watcher) in the no-text refresh
commit, causing a full replay of previous session messages whenever codex
or claude-code sessions are respawned by the health poller.

Fix: add replayHistory option (default false) to startWatchingSpecificFile,
startWatchingFile, startWatching, and activateFile. Only the daemon-restart
restore paths in restoreFromStore() pass replayHistory: true — these are the
cases where the browser genuinely needs to see recent history after
reconnecting. Session respawn/restart paths do not replay.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Add regression tests to both codex-watcher and jsonl-watcher that assert:
- startWatchingSpecificFile / startWatchingFile do NOT emit pre-existing
  content by default (replayHistory defaults to false)
- Only when replayHistory: true is explicitly passed (daemon restore path)
  is historical content replayed

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

History is persisted in the timeline store and served to browsers via
the timeline replay endpoint. Replaying JSONL/rollout files at watcher
startup was always wrong — it duplicates events the browser already
received, regardless of whether the daemon or session restarted.

Remove replayHistory option and all emitRecentHistory calls from
startWatchingSpecificFile, startWatchingFile, startWatching, and
activateFile. Watchers now exclusively track new content from fileOffset.

Tests updated to assert: watcher startup never emits pre-existing content.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…m startup

Export emitRecentHistory so tests can call it directly. Update
emitRecentHistory and stable-eventId tests to not rely on watcher
startup triggering history replay (which was removed per no-replay rule).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

On macOS APFS (nanosecond mtime) fileB was newer than fileA because it
was written a few ns later in beforeEach. watchFile saw fileB as newer
and switched the 'jsonl-a' watcher away from fileA, so refresh() drained
fileB (empty) and never emitted the expected event.

Fix: create fileB first, then fileA, and use utimes to advance fileA's
mtime +2s past fileB — same technique used for the codex-watcher HFS+
fix. Guards both nanosecond-precision APFS and 1-second HFS+ resolvers.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…indows

When the daemon launches via a Windows Scheduled Task or Startup shortcut,
the restricted environment cannot resolve 'cmd.exe' through PATH, causing
CreateProcess to fail with 'File not found' and all sessions to enter the
error state with a runaway restart loop.

Fix: resolve cmd.exe via COMSPEC env var (always set by Windows), falling
back to %SystemRoot%\system32\cmd.exe. Also convert CWD backslashes to
forward slashes to avoid node-pty's internal path.resolve error 267 on
some versions.

Tests: 3 new cases for COMSPEC resolution, fallback path, and CWD slash
normalization.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

conpty: update 7 spawn assertions from bare 'cmd.exe' to
stringMatching(/cmd\.exe$/i) so they pass on actual Windows where the
absolute COMSPEC path is used (e.g. C:\Windows\system32\cmd.exe).

p2p-orchestrator: afterEach now cancels all active runs before deleting
the temp dir. Background async ops (idle polls, file reads) from parallel
hops were still in flight when the dir was deleted, producing unhandled
ENOENT promise rejections that Vitest classified as test failures.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…codex-watcher-retrack

checkNewer() returns false when both files are created within the same second on
HFS+ (1s resolution). Use utimes() to set runningFile mtime +2s past oldFile
so maybeSwitchActiveFile() reliably detects it as newer on all platforms.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Three root causes fixed:

1. **Duplicate watchdog loops**: restartWindowsDaemon only killed the daemon
   node process, leaving the old watchdog cmd.exe alive. The old watchdog
   respawned the daemon (with stale code) while a new watchdog was also
   spawned — causing duplicate loops and version-mismatch restarts.
   Fix: kill the entire watchdog process tree (taskkill /f /t) before
   spawning a fresh hidden watchdog.

2. **schtasks /Create with visible window**: bind created the scheduled
   task with a bare node command (/TR "node.exe ... start --foreground"),
   then tried /Change to VBS. If /Change failed silently, every login
   launched a visible cmd.exe window.
   Fix: create the task directly with /TR "wscript launcher.vbs".

3. **Upgrade cleanup popups**: upgrade batch used `start "" cmd /c cleanup`
   which flashes a visible window.
   Fix: use `start "" /min cmd /c cleanup` to minimize.

Also: VBS launcher now prioritized over scheduled task in restart flow,
and all spawn() calls use windowsHide: true.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…unused vars

- Rewrite windows-daemon.test.ts to match new killWatchdogTree behavior
  (wmic parent lookup + taskkill /t tree-kill instead of bare taskkill)
- Update test priority: VBS first, then schtask, then startup shortcut
- Add test for force-kill fallback when tree-kill misses daemon
- Remove unused nodeExe/imcodesScript in bind-flow (schtasks now uses VBS directly)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>